FEATURE: Use custom transformer for flow exceptions #242
Conversation
|
It is not done yet but hopefully the idea is not so wrong. |
markusguenther
force-pushed
the
feature/localized-exceptions
branch
from
0e66ff8
to
84b3c95
Compare
|
Hopefully localized now all error messages and warnings we have in the codebase. 
|
markusguenther
force-pushed
the
feature/localized-exceptions
branch
from
6acb336
to
4023457
Compare
|
Thanks for the feedback, updated the labels! |
|
Hmm when I checkout the branch and build the module I now get 2 error messages: |
I guess that one error is thrown by the application itself and the other comes from the backend as a flash message. |
|
In the end with the PR #241 that should not happen anymore. |
The behavior did not change, just the labels are different now and as I mentioned, with the validation before creating the tag we prevent having two flash messages. |
markusguenther
force-pushed
the
feature/localized-exceptions
branch
from
1d82b4c
to
47c2d35
Compare
Sebobo
force-pushed
the
feature/localized-exceptions
branch
from
47c2d35
to
a3bf910
Compare
The t3n GraphQL package includes a transformer that bypasses Flow Framework exceptions in GraphQL error handling. The error currently lacks the exception code as part of the information. By including this code (often a timestamp), we can render custom error messages in the backend and support localization.
Sebobo
force-pushed
the
feature/localized-exceptions
branch
from
bab4ec5
to
6646240
Compare
|
Thx! I squashed the commits a bit and removed the bundled files. Also I fixed the duplicate error message |
The t3n GraphQL package includes a transformer that bypasses Flow Framework exceptions in GraphQL error handling. The error currently lacks the exception code as part of the information. By including this code (often a timestamp), we can render custom error messages in the backend and support localization.
Relates: #240